-
Notifications
You must be signed in to change notification settings - Fork 811
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Simplified Audiobook example #2232
Conversation
Well...I got inspired. 😁 The Audiobook examples now use the I also chose a freely available audiobook from the kind people at Archive.org and LibriVox. It also happens to be Alice's Adventure's in Wonderland because Mad Hatters. Cheers! |
A nice simple example. I would tweak it slightly thus:
There is a difference between the Audiobook (CreativeWork) and the actual bytes of the media object. |
@RichardWallis so...this may be a bit Range-14-like, but... This trimmed example (from your post earlier--and on which I'm basing further commits to this PR) introduces some confusion (at least in my coffee-enhanced cranium): {
"@context": "http://schema.org/",
"type": "Audiobook",
"@id": "https://archive.org/details/alices_adventures_1005_librivox",
"contentUrl": "https://archive.org/download/alices_adventures_1005_librivox/AlicesAdventuresInWonderlandV5_librivox.m4b",
"mainEntityOfPage": "https://archive.org/details/alices_adventures_1005_librivox"
} That, afaict, says that I realize that "naming things is hard," but I wanted to double check with you (et al) prior to making these changes. This is more or less why I'd used |
To avoid this being stalled indefinitely, @RichardWallis how do you feel about my removing the |
To avoid confusion, either the My personal preference would to either change the To my mind it is more important to identify the thing/entity than the page(s) that may represent it. Having said that, out in the real world it is often the case that the page URL is the only available identifier. |
@RichardWallis sorry for the wait on this one. I went with the |
Github is reporting conflicts in data/ext/bib/bsdo-audiobook-examples.txt - could you take a look? |
The earlier JSON-LD version looked like it was extracted from the RDFa and had some cruft from that conversion left over. It's gone now, and should be simpler and more easily reused.